projects / ostree.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: c4998ab) | patch
OstreeGpgVerifier: Take the signed data as a GBytes
authorMatthew Barnes <mbarnes@redhat.com>
Mon, 16 Mar 2015 17:01:55 +0000 (13:01 -0400)
committerMatthew Barnes <mbarnes@redhat.com>
Mon, 16 Mar 2015 20:37:11 +0000 (16:37 -0400)
commitf47693440dd2c418464c9aff60300bcae4e407c0
tree02eb79a78d4e380704185ed96dd70824ad729281tree | snapshot
parentc4998ab33f7db752c176f6a0c6ead14f0bfffe9bcommit | diff
OstreeGpgVerifier: Take the signed data as a GBytes

Similar to c2b01ad.  For some reason I was thinking the commit data
still needed to be written to disk prior to verifying, but it's just
another artifact of spawning gpgv2 (predates using GPGME).

Makes for a nice cleanup in fetch_metadata_to_verify_delta_superblock()
as well.
src/libostree/ostree-gpg-verifier.c diff | blob | history
src/libostree/ostree-gpg-verifier.h diff | blob | history
src/libostree/ostree-repo-private.h diff | blob | history
src/libostree/ostree-repo-pull.c diff | blob | history
src/libostree/ostree-repo.c diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.